Info

Closes #171

For most destructive buttons, including ones directly cause API actions when clicked, as well as some other permanent actions like competing a pickup event, it now asks for confirmation first.

Background: a pickup event was accidentally marked as completed

Changes

• Added a useConfirm hook that manages a confirmation modal
• Used the hook for several destructive buttons

Type of Change

• Bug Fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as
  expected)
• Logistics Change (A change to a README, description, or dev workflow setup like
  linting/formatting)
• Continuous Integration Change (Related to deployment steps or continuous integration
  workflows)
• Other: (Fill In)

Testing

I have tested that my changes fully resolve the linked issue ...

• locally on Desktop.
• on the live deployment preview on Desktop.
• on the live deployment preview on Mobile.
• I have added new Cypress tests that are passing.

Checklist

• I have performed a self-review of my own code.
• I have followed the style guidelines of this project.
• I have documented any new functions in /src/lib/* and commented hard to understand areas
  anywhere else.
• My changes produce no new warnings.

Screenshots

^ note: i'm not sure if the backend does delete all of a collections' items

this one has a different cancel button label to avoid the double cancel: